Search Results: "stark"

18 January 2007

Robert McQueen: LCA and hiring

I’m in Sydney for LCA 2007 this week, and this should also be my debut post on the conference planet. This is the first time I’ve made it to the other side of the world for this conference, and I’m really glad I came. It’s definitely one of the cooler conferences I’ve been to, slickly run and with an excellent programme of talks, so massive congratulations and thanks are due to the organisers and volunteers. The weather’s a stark contrast to the French Alps (I was skiing last week!), although thankfully it’s quite mild at the moment and not gotten too hot for a Pom like me. :D It’s always cool to catch up with people who I’ve not seen for a while, and put names to faces for a whole load of others I’ve not met yet. If you’re around, reading this in time, and interested in the Telepathy VOIP/IM framework, my talk is today (Friday) at 11am. If shameless bribes help, I’ve also got some funky Collabora and Telepathy shirts I need to give away before I head back to the UK. The second bit is that Collabora’s looking for a couple of people to either join us in Cambridge (UK) or work with us as a subcontractor. We’re currently doing loads of cool and totally open source stuff with IM, voice & video streaming and collaboration technologies. We’re looking for people with experience with some/many/all of C, Python, Glib/Gtk, D-Bus, GStreamer and RTP. If you’re interested, send mail to jobs( )collabora.co.uk, or if you’re around at LCA then come and find me if you want a chat.

2 November 2006

Edd Dumbill: XTech 2007 is go!

I've just published the call for participation for XTech 2007.The theme for this year’s conference is “The Ubiquitous Web”. As the web reaches further into our lives, we will consider the increasing ubiquity of connectivity, what it means for real world objects to be connected with the web, and the increasing blurring of the lines between virtual worlds and our own.XTech will have its usual four tracks: Applications, Browser Technologies, Core Technology, Open Data. Keynotes addresses will be given by Adam Greenfield, author of “Everyware: The Dawning Age of Ubiquitous Computing”, Gavin Starks of Global Cool and designers of the future Matt Webb and Jack Schulze.Head over to the call pages and submit your proposal. The deadline is 15 December 2006. The conference itself is in Paris, France, 15-18 May 2007.
ExpectnationThe publication of the XTech call is doubly exciting for me. XTech 2007 will be the first conference to be managed completely from Expectnation, the software I've been building over the course of the last year.Expectnation is a web-based system for managing conferences and training events. Right now we're conducting tests with some customers, and are working hard on readying the system for a public trial.The particular strengths of Expectnation include the management of speakers, proposals and delegates. If you would like to stay informed of our progress, there's a place to sign up for news on the Expectnation home page.

19 September 2006

Edd Dumbill: EuroFoo reflections

I got an enormous amount out of the just-finished European FooCamp, with lots of thoughts sparking off and interesting things to consider. Jon Mountjoy proposed a theory to me that Web 2.0 and the enterprise weren't in fact as far apart as a naive observe might imagine. He reckons that mashups, tagging and the like do happen within the enterprise, and in fact are often solving harder problems than found in the wilds of the web. There is a lot in common between Web 2.0 and SOA (even aside from buzzword compliance factors). This is a theme I'd like to follow through. Who are the hackers on the inside of companies, and what stories do they have to tell? Gavin Starks from Global Cool really opened our eyes again to the problem of the environment, and introduced the interesting position that Global Cool are taking. If you want to do anything real right now to avoid catastrophic consequences, it's too late to wait for government initiatives to bear fruit. Private citizens must act too. And that's the aim of Global Cool: educating and lobbying the individual, not the government. I was struck, as were others, by the unfortunate irony that conferences have a big environmental cost in the travel involved, as we sat there among people from many countries. I want to now investigate how XTech could be better in this regard, through carbon offsetting and similar schemes. I guess being in Paris is already a good start, as trains are apparently only 25% as polluting as planes, though this still seems like a lot! Claus Dahl led an interesting and wide-ranging discussion about Second Life as a prototyping space for real life invention. Too many themes there to summarise neatly, but we did have an entertaining side discussion about Second Life's potential environmental impact due to CPU consumption and data centers. One suggestion was that objects and activities could be annotated in-world with their environmental cost. Simon Willison energetically explained OpenID, a decentralized identity system proposed by SixApart and already live in systems such as LiveJournal. It attempts to solve the problem of a username and password pair for every site you visit, without the controversy of centralisation suffered by projects such as Microsoft's passport. Simon demonstrated a proof of concept that I think will be a very neat answer to site providers who ask "why should I support OpenID?" (Sneak preview: because if you don't, it's going to be astonishingly easy for a middleman to provide it, and you wouldn't want that.) I also took time to learn about something I'd been interested in but not known much about, 3D printing and "fabbing". Simon Wardley led a great overview of current systems for 3D printing and their various attributes, and indicated where the current trends were going. It doesn't seem so unrealistic that there'll soon be affordable 3D printing bureaux similar to walk-in reprographic facilities like Kinkos. Plenty more went on that I've not got time to transcribe, but I think will flavour my thinking over the months to come. I was fortunate to be among some incredibly intelligent and welcoming people. My thanks to O'Reilly for putting this on, and to everyone else who went for being inspiring companions. Oh, one more thing. Belgians are excellent at confectionery.

4 September 2006

Benjamin Mako Hill: Musical Beds

During Wikimania, I was explaining to someone that Aziz Ridouan (Audionautes) was staying at Elizabeth Stark's apartment, that Elizabeth Stark was staying at Jean-Baptiste Soufron's apartment, and that Jean-Baptiste Soufron was staying at my apartment. In fact, all four of us have slept at least one night at both the Acetarium and at Jean-Baptiste's apartment in the last month and a half.

13 June 2006

Michael Janssen: Weekend Weeviews: The Iron Giant, Brazil

Wow, a semi-regular posting.

The Iron Giant

Small town america in the late 50s doesn't know what hit it. Science fiction is in it's hayday and the nation is on a hairpin trigger when a big robot falls from the sky and is discovered by a small boy. I had heard much about this movie and everyone I knew who saw it liked it. I have to tell you: the hype is well deserved. The story is compelling and heartening, good for children and adults alike, and the humor throughout is well done. Characters are voiced well. The story obviously revolves around the giant. Most of the story is centered around keeping the monstrosity hidden, which doesn't succeed for long. The government eventually figures it out and starts shooting, and then things really get interesting. The ending was just as fun to watch as the beginning, although I think they copped out on the very end, leaving it with a light note. It would have been really nice to see it end in a bitter-sweet tone. The Giant gets a 9. (imdb)

Brazil

One of the things I remember hearing about Brazil is that it was "Terry Gilliam's Directorial Masterpiece". It certainly is at that. In the 20th century somewhere, a clerical error causes a great movie plot. A futuristic society is thrown into disarray by a simple error in typing, starting with the death of an innocent man, and then the coverup of the century. The protaganist is in a dead-end job, but seems to be perfectly fine with it, until the girl of his dreams literally walks into his life. Gilliam and his cinematographer create a beautifully blocky and dull grey industrial wasteland set in stark contrast with the beautiful dreamland. The subplots don't obscure the main line which is compelling and kept me wanting more even though it clocks in at over 2 hours. The ending was unexpected and well done at the same time, and I couldn't see it done any other way. The directors cut is the only way to go with this one, and I haven't even seen the studio cut.
Brazil is berriffic, and scores a 12. (imdb)

27 January 2006

Uwe Hermann: Ehren Starks - One Big Hope

Ehren Starks album art Ahh, I haven't played a purely instrumental piano piece for a while, so here goes. Ehren Starks with a wonderfully calm piece which gets more energetic near the end... Song: Ehren Starks - One Big Hope (4:50 min, 4.5 MB)
License: CC-by-nc-sa 1.0
Source: magnatune.com
Purchase from: Magnatune

21 January 2006

Edd Dumbill: Why Rails?

When I moved this blog from being Zope-backed to using Rails several people got in touch to ask why. This is a brief explanation of why I've moved.Firstly I should point out I've had a long and mostly happy experience with Zope. I got into Zope originally because I'd spent some time in constructing web frameworks from scratch (we're talking 1995-1999 here) and found that not only does a framework need good templating, it needs reusable components within that.Zope seemed like a good fit, so I spent some time getting up to speed and was happy there. However, there were some things that didn't make me feel completely comfortable. Zope offered a very stark choice between developing through the web based interface (DTML methods, etc.) and writing raw Python. To do really useful stuff, you had to get into the Python side of things, but also learn a lot about Zope guts that wasn't really well documented.I spent more time than I probably should have had to reading Zope's own source code in order to figure out how things worked. Fine, for my own silly little projects, but not practical in general. It was hard to get the overall view of a project, and hard to test. The learning curve was a little too steep, I suppose.
So, once I'd got to a certain point I stopped, and looked around for a platform that gave me more code visibility and testability. Loyal readers will know I've looked at ASP.NET and Python, Quixote and Cheetah. ASP.NET I rejected because I didn't view Mono's web application server as mature enough at the time, and I also had reservations about ASP.NET's non-free baggage. Python, Quixote and Cheetah looked a lot more friendly.What I wrote about Quixote and Cheetah at the time was "this combination isn't adequately presented and described anywhere." These were good technologies, but not integrated as a framework. I started work on integrating them, and made some interesting progress. I was correct that Python lacked a solid modern framework, and the time was certainly right for it, as we can now see by the emergence of Django and TurboGears.
However, at the same time I started looking at Rails and found out that it did pretty much what I wanted. To be honest, I'd avoided it for a while as a friend once did me the disservice of calling Ruby a cross between Python and Perl. "Why ruin Python?", I thought. And it takes me a while to get over the hype barrier before I conclude that there's a "there" there.
Now I've been using Rails for a while, I find its attractions have changed for me. The thrill of not having to write basic functionality over and over again has given way to more select pleasures. Writing in Ruby itself is a rewarding experience, as its idioms become plainer over time.Sure, you can write Java or Perl in any language, and that's where I started off. But the subtle elegance of the Ruby idiom is a slowly appreciated and highly satisfying flavour. For developers who consider themselves as poets and artists too, I can't think of a better language.

19 January 2006

Clint Adams: Not adjusted for inflation

Twice upon a time, there was a corporation called Company B. Ironically, their bugle player quit two days before the beginning of this story. Two days after the bugle player quit, something sinister was happening at Company B. To better understand it, we need to go back in time a bit. So this next part happens well before the beginning of the story. Once upon a time, Company B was run by a middle-management team known as Team Alfalfa. These guys were young and na ve and inexperienced, but idealistic and somewhat morally pure. They certainly didn't expect the bugle player to quit. They were surprised by almost every one of the things to come. When they hired a Belarussian, they were surprised when he quit shortly thereafter and moved to Hampshire County in Massachusetts. They were surprised when the owners of Company B hired Team Buckwheat. Team Buckwheat was a group of power-hungry jerks, who were hired because they had Experience and Vision. Company B needed to grow, because Progress is important, and anyway, how else would the owners be able to bilk the company of millions of dollars through fraud and mismanagement if the company didn't grow big enough to amass millions of dollars in the first place? The thirst for power was great within each member of Team Buckwheat, and they collectively vowed to take over the company. Through trickery and deceit, they sabotaged Team Alfalfa. Team Alfalfa mistakenly believed that its power hold was strong and that it could threaten to hold the company's business hostage, but it was very much mistaken. Slowly but surely, Team Buckwheat started to drive Team Alfalfa out of the company until only two members remained. In fact, their lust was so great that they began vying for power amongst themselves before they had succeeded completely in their purge of the ranks of Team Alfalfa. They employed evil and complicated manipulations and machinations, until only two of them remained as well. As only two, they were much less powerful, and as they saw the danger and became afraid, they clung to one another and allied. Losing faith in Team Buckwheat, the owners of Company B hired the Grey Knight to continue the work of rapidly growing the company in order to make enormous profits. The Grey Knight came in and exuded Calmness and Rationalness, and provided a stark contrast to the meanness and cruelty that Team Buckwheat inflicted upon its subordinates. So some unlikely bedfellows among the grunts and peons formed an alliance, and with the reluctant aid of the Grey Knight, they had the remnants of Team Buckwheat fired based on flimsy pretexts, while the remnants of Team Alfalfa watched from the sidelines. The peons and grunts were na ve and overly hopeful in the Grey Knight, who was not as noble as he seemed. After a few months of everything functioning better than it had ever done before, he brought in his friends, Team Corn. Team Corn was power-hungry as well, but more patient. Unlike Team Buckwheat, which had been cobbled together from strangers, Team Corn stuck together and moved from company to company, leaving waves of disgust and resentment in its wake. These people immediately took steps to secure their power base. Where things had been transparent and group-oriented before, they were made obscure and individualized. Each project was assigned to a single person. All communication regarding each project was required to go directly and privately to the responsible person. Discussing a project with anyone else was a breach of protocol. If the responsible person fell sick or left the country for mysterious reasons, all activity on that project would cease. Accomplishments were discouraged, and simulating the appearance of much effort and progress was encouraged. The members of Team Corn were stunted in their moral development. They believed that one was either with them or against them. Those who chose to be sycophants were given rewards and promotions, no matter how incompetent and unqualified they were. Those who did not were oppressed and punished. Objections and questions to ill-advised policies were met with hostility, and if anyone ever took a principled stand, Team Corn became fraught with confusion; they could not conceive of a reason one might act for the greater good or based on conscience rather than to do what would advance one's own interests. After a very long time, this fundamental lack of comprehension of their own evil led to their downfall, but that small bit of justice was tempered when Team Durum came in to replace them. Team Durum wasn't as bad as Team Corn, but boy did it suck.

Next.

Previous.